Linked transaction camera with cached video log

ABSTRACT

A management terminal manages a plurality of Self-Service Terminals (SSTs) for customer-assistance, transaction overrides, theft determinations, and transaction security audits. One or more overhead cameras stream real-time video of the transactions being processed at the SSTs to a server. Transaction data produced in real time at the SSTs are also provided to the server. The video is correlated with the transaction data and evaluated for security events. The video is also cached on the server. An operator of the management terminal can access a video review interface based on events and/or information visually gleaned by the operator during the transactions. The interface permits the operator to view a configured cached portion of the video captured for any given transaction to provide context to the operator for determining whether to perform or whether not to perform a transaction audit.

BACKGROUND

Self-checkouts at retail stores have become commonplace in the industry.A staff-operated terminal typically monitors the self-checkout terminalsfor purposes of assisting customers that are having problems completingtheir transactions and identifying customer thefts. During busy customertraffic, the staff can be overwhelmed with needed or perceivedtransaction interventions.

Many times, the staff has to make split second decisions as to whetherto audit customers for potential theft at the self-checkout terminals.The staff-operated terminal may provide detected information that couldbe useful to the staff but often that information requires moreinspection by the staff to decide whether a customer transaction shouldbe audited. By the time the information is investigated, the customermay have already checked out and left the store.

Staff may have well-founded suspicions that a customer is engaged intheft and yet no security event is raised for the transaction at thestaff-operated terminal. In these situations, the staff does not want toperform an audit of the customer based on a suspicion because audits cancreate customer animosity and there were not any security-relatedevents, which were raised at the staff-operated terminal.

So, in most cases the staff elects not to perform transaction auditsbecause the staff is overwhelmed assisting in transaction overrides atthe self-checkout terminals, busy answering customer questions, and/orbusy evaluating raised security events. Consequently, the staff is morelikely to simply clear any security events than engage customers intransaction audits.

Theft from fake scanning bar coded items and theft from swapping lessexpensive bar codes onto more expensive items remain problematic for theindustry. The staff is simply stretched too thin to effectivelydetermine whether to perform transaction audits and any raised securityevents are often not accurate enough to rely on.

SUMMARY

In various embodiments, methods and a system for self-checkout securityvideo review are presented.

According to an embodiment, a method for processing self-checkoutsecurity video review is provided. A video streamed from a camera andcaptured by the camera for a transaction area of a transaction terminalis cached within a cache. Transaction data associated with a transactionoccurring at the transaction terminal is obtained and the transactiondata is linked to portions of the video residing in the cache. A requestfor a video clip of the transaction is received. The video clip and thetransaction data are provided to a management terminal based on therequest by taking a configured amount of the video from the cache thatstarts at a first configured time before an event and continues througha second configured time after the event.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a system for processing self-checkout securityvideo review, according to an example embodiment.

FIG. 2 is a diagram of a method for processing self-checkout securityvideo review, according to an example embodiment.

FIG. 3 is a diagram of another method for processing self-checkoutsecurity video review, according to an example embodiment.

DETAILED DESCRIPTION

FIG. 1 is a diagram of a system 100 for processing self-checkoutsecurity video review, according to an example embodiment, according toan example embodiment. It is to be noted that the components are shownschematically in greatly simplified form, with only those componentsrelevant to understanding of the embodiments being illustrated.

Furthermore, the various components (that are identified in the FIG. 1)are illustrated and the arrangement of the components is presented forpurposes of illustration only. It is to be noted that other arrangementswith more or less components are possible without departing from theteachings of processing self-checkout security video review, presentedherein and below.

The system 100 permits an operator of a management terminal to access aninterface and review a cached portion of a transaction at any of themanaged transaction terminals. Overhead cameras proximate to thetransaction terminals stream real-time video of the transaction areas toa server. The server caches the video and the operator can access aninterface from the management terminal to review a preconfigured amountof video from the video cache for any given transaction for purposes ofdetermining whether to perform or whether not to perform a transactionaudit.

The system 100 includes cameras 110, transaction terminals 120, terminalstatus lights/speakers 130, a management terminal 140, a server 150, anda security system 160.

Each transaction terminal 120 comprises a plurality of peripheraldevices 121 (card reader, printer, media handling device, touch displayscreen, keypad, etc.), one or more processors 122, and a non-transitorycomputer-readable storage medium 123 comprising executable instructionsrepresenting a transaction manager 124 and a transaction agent 125.

Management terminal 140 comprises one or more processors 141 and anon-transitory computer-readable storage medium 142 comprisingexecutable instructions representing a transaction manager 143 and anevent interface 144.

Server 150 comprises one or more processors 151, a video cache memory152, and a non-transitory computer-readable storage medium 153comprising executable instructions representing a transaction manager154 and an event interface 155.

Security system 160 correlates transaction video captured by cameras 110with transaction data generated by transaction managers 124 oftransaction terminals 120. Security system 150 also generates securityevents based on the correlations and security rules. Still further,security system 150 correlates the security events with correspondingportions of the captured video.

Terminal status lights/speakers 130 are activated by security eventsraised from security system 160, states of transaction terminals 120,transaction manager 143 of management terminal 140, and transactionmanager 154 of server 150. Activation includes illumination of one ormore colored lights 130 and/or playing a security tone or audio overspeakers 130.

During operation of system 100, customers perform self-checkouts onterminals 120 while cameras 110 capture video of each transaction areafor each terminal. The video is streamed from cameras 110 to server 150.Concurrently, transaction data being generated at the terminals 120 aresent to transaction manager 143 of management terminal 140 and,optionally, transaction data can be displayed on a display associatedwith management terminal 140 by the operator of terminal 140.Additionally, the transaction data may also be sent to transactionmanager 155 of server 150.

Video data streamed from cameras 110 may be permanently stored on server150 and indexed and linked with the corresponding transaction data andsecurity events. Moreover, the video data for each transaction at eachterminal 120 is cached in cache memory 153 (cache 153). Event interface144 may be used to set the time duration for which each video capturedfor each transaction is maintained in cache 153. That is, operator ofterminal 140 accesses event interface 144 to interact with eventinterface 156 of server 150. The time duration is configured by theoperator. The time duration begins at a period of time that precedes anygiven start of a transaction precedes a time stamp associated with agiven security event raised by security system 160. The same time periodof time or a different operator configured period of time thatidentifies a length of time after a transaction ends and/or after thetime stamp of the security event. Event interface 156 constructs a videoclip from the video in cache 153 that starts at the configured period oftime before transaction start or event time stamp and continues pasttransaction end or event time stamp for the same configured period oftime or for a different operator-defined second period of time.

Event interface 156 caches the video and indexes time stamps within thevideo to a given terminal identifier for a given terminal 120 and agiven transaction identifier for a given transaction. Event interface156 stores the video captured by cameras 110 in cache along withmetadata associated with the corresponding terminal identifiers andtransaction identifiers. The length of time before and after thetransaction/event timestamp is defined by the configurable period oftimes referenced above and set by the operator of management terminal140 through event interface 144. Event interface 156 uses theconfigurable period or times to derive or construct a video clip fromthe video within the cache 153.

Management terminal 140 also receives transaction data and any raisedsecurity events from security system 160. An operator may elect toreview the video of any given transaction area for any given terminal120 and corresponding transaction by requesting a corresponding videoclip using event interface 144. Upon receiving a video review request,event interface 156 accesses cache 153 using the transaction identifierfor the transaction requested, constructs the corresponding video clip(based on the configured before and after time periods), and streams thevideo clip or provides a link to the video clip back to event interface144 where the operator can review the video in real time on a display ofterminal 140. A security event may cause transaction manager 155 toalert event interface 156 and automatically stream the correspondingtransaction's video clip (using the configured period of time/timesbefore and after the event timestamp) to event interface 144 orautomatically display a popup window within event interface 144 with alink for displaying the video clip once the link is activated by theoperator.

Within event interface 144, the transaction data (such as items scannedfor the transaction and item prices) may be presented along side of thevideo clip being played for the transaction area. In this way, theoperator can view the recorded items scanned/entered for the transactionwhile simultaneously viewing the video clip for the transaction area.This provides the operator with the necessary context for thetransaction while the video clip is being played. The operator may alsopause, fast forward, and rewind the video being played within eventinterface 144.

In an embodiment, as each transaction item is scanned it is associatedwith a time stamp that corresponds to a time stamp in the video capturedfor any given transaction. The operator when reviewing a transactionvideo clip may click on a given displayed transaction item and eventinterface 144 automatically skips ahead or rewinds from a current pointin the video being played to the time stamp within the video clip thatcorresponds to the selected item, which was selected by the operatorwithin event interface 144.

Security system 160 may perform its own real-time analysis of thetransaction items within the video stream for purposes of raisingsecurity alerts sent to transaction manager 143. Transaction manager 143then uses an Application Programming Interface (API) to event interfaces156 and 144 for purposes of having predefined security eventsautomatically retrieve the corresponding video clip associated with thetransaction from cache 153 and automatically initiating the video clipor automatically providing a link to the video clip within eventinterface 144 for operator review.

Again, the operator is in control of when or if a video clip associatedwith a given transaction of a given transaction terminal 120 is playedwithin event interface 144. Moreover, the period of time for which thevideo clip is captured both before and after the transaction/eventtimestamp can be configured by the operator within event interface 144(interface 144 interacts with event interface 156). Further, if securitysystem 160 is configured to display a shorter or a larger amount of thetransaction video associated with a security event, this is overriddenby event interface 156 and a shorter or a longer length of timeassociated with the configured period of time before and after thesecurity event or the transaction as a whole is provided in thedelivered video clip from cache 153.

In an embodiment, any generated security events for a transaction arealso time stamped within the corresponding video clip and the securityevents are presented along with the transaction items within the videoclip retrieved from cache 153. A selection of a given security eventwill automatically cause the video clip being played within eventinterface 144 to skip forward or backward and play the video clip at thetime stamp associated with the security event.

It is noted that not all security events require a review by theoperator of management terminal 140; however, such types of securityevents may still be displayed with the video clip selected for play bythe operator within event interface 144. So, when the operator decidesin real time to review a transaction that is occurring at a terminal120, the then-existing and already scanned items are listed along withany raised security events. Both the transaction items and the securityevents are linked within the video clip for quick review by theoperator. Furthermore, because the video clip includes video before andafter each event was raised and before and after each item was scanned,the operator is provided a full visual context of any given securityevent and/or item scanned from the video clip retrieved from cache 153.

System 100 permits the operators of management terminals 140 to define acontext before and after a transaction or security event for which avideo clip is derived from video in cache 153. Because cache 153 is inmemory, retrieval and play of the video clip is fast and efficient. As aresult, operators get a real time or near real time visual review oftransactions with a full context. Moreover, the video clip is timeindexed and linked to both transaction data (item scans, paymentinformation, etc.) and the security events raised by security system160. So, the operator can quickly view specific portions of thetransaction for theft when needed.

System 100 also substantially reduces the workload of the operator sothat determinations as to whether to stop a customer before the customerexits a store and an operator audit of the transaction may occur.

In an embodiment, event interface 144 may also include an option for theoperator to raise an alert to transaction manager 143 when an audit isneed or when a theft is suspected. By activating the option within eventinterface 144 while the operator is visually inspecting thecorresponding video clip, transaction manager 143 can cause terminalstatus lights 130 to illuminate in a predefined color or with apredefined effect and/or cause speakers 130 to play an audible voiceinstruction and/or distinguishable audible sound/beep.

In an embodiment, terminals 120 include SSTs, AMTs, self-grocery storecheckouts, and/or kiosks.

In an embodiment, management terminal 140 can include a speciallyconfigured SST, Point-Of-Sale (POS) terminal, teller terminal, a tabletcomputer, a laptop computer, a desktop computer, and/or a mobile phone.

In an embodiment, server 150 is a cloud processing environment (cloud)comprising multiple servers logically organized as a single environment.

These and other embodiments are now discussed with reference to theFIGS. 2-3.

FIG. 2 is a diagram of a method 200 for processing self-checkoutsecurity video review, according to an example embodiment. The softwaremodule(s) that implements the method 200 is referred to as a“transaction video clip cache manager.” The transaction video clip cachemanager is implemented as executable instructions programmed andresiding within memory and/or a non-transitory computer-readable(processor-readable) storage medium and executed by one or moreprocessors of a cloud/server. The processor(s) of the cloud/server thatexecutes the transaction video clip cache manager are specificallyconfigured and programmed to process the transaction video clip cachemanager. The transaction video clip cache manager has access to one ormore network connections during its processing. The network connectionscan be wired, wireless, or a combination of wired and wireless.

In an embodiment, the transaction video clip cache manager executes onserver 150. In an embodiment, server 150 is part of a cloud processingenvironment.

In an embodiment, the transaction video clip cache manager is all orsome combination of transaction manager 155, event interface 156, and/orsecurity system 160.

At 210, the transaction video clip cache manager caches a video streamedfrom a camera and captured by the camera for a transaction area of atransaction terminal in a cache.

In an embodiment, at 211, the transaction video clip cache managerreceives the video from the camera that is situated above or overhead ofthe transaction area.

In an embodiment of 211 and at 212, the transaction video clip cachemanager offloads the video from the cache to storage on a server after aconfigured period of time after the transaction ends.

At 220, the transaction video clip cache manager obtains transactiondata associated with a transaction occurring at the transactionterminal.

In an embodiment, at 221, the transaction video clip cache managerobtains one or more security events raised by a security system for thetransaction.

At 230, the transaction video clip cache manager links the transactiondata to portions of the video residing in the cache.

In an embodiment of 221 and 230, at 231, the transaction video clipcache manager links the one or more security events to the portions orto other portions of the video residing in the cache.

In an embodiment, at 232, the transaction video clip cache managerindexes each item identified in the transaction data with thecorresponding portion of the video based on timestamps associated withthe corresponding item and the corresponding portion of the video.

In an embodiment of 232 and at 233, the transaction video clip cachemanager provides the transaction data as a list of the items, each itemof the list having metadata, and the corresponding metadata associatedwith each item references a specific time location within the videoclip.

At 240, the transaction video clip cache manager receives a request fora video clip of the transaction.

At 250, the transaction video clip cache manager provides the video clipand the transaction data to a management terminal based on the requestby taking a configured amount of the video from the cache that starts ata first configured time before an event and continues through a secondconfigured time after the event.

In an embodiment of 232 and 250, at 251, the transaction video clipcache manager provides the transaction data as a list of the items, eachitem of the list having metadata, and wherein the corresponding metadataassociated with each item references a specific time location within thevideo clip.

In an embodiment, at 252, the transaction video clip cache managerprovides the transaction data and the video clip to an interface of themanagement terminal.

In an embodiment of 252 and at 253, the transaction video clip cachemanager processes an API to provide the transaction data and the videoclip to the interface.

In an embodiment, at 254, the transaction video clip cache managerprovides the video clip to the management terminal as a link.

In an embodiment, at 255, the transaction video clip cache managerreceives the first configured time and the second configured time as aconfiguration setting from an operator of the management terminal.

In an embodiment, at 256, the transaction video clip cache manageridentifies the event as a security event having a timestamp thatcorresponds to a specific location within the video stored in the cache.

FIG. 3 is a diagram of another method 300 for processing self-checkoutsecurity video review according to an example embodiment. The softwaremodule(s) that implements the method 300 is referred to as a“transaction video clip manager.” The transaction video clip manager isimplemented as executable instructions programmed and residing withinmemory and/or a non-transitory computer-readable (processor-readable)storage medium and executed by one or more processors of a managementterminal. The processors that execute the transaction video clip managerare specifically configured and programmed to process the transactionvideo clip manager. The transaction video clip manager has access to oneor more network connections during its processing. The networkconnections can be wired, wireless, or a combination of wired andwireless.

In an embodiment, the transaction video clip manager executes onmanagement terminal 140. In an embodiment, management terminal 140 is aspecially configured SST, a POS terminal, a laptop, a tablet, a desktopcomputer, and/or a phone.

In an embodiment, the transaction video clip manager is all of or somecombination of the transaction manager 143 and/or event interface 144.

The transaction video clip manager interacts with event interface 156and/or method 200 over a network connection (wired, wireless, or acombination of wired and wireless.

At 310, the transaction video clip manager requests a video clip of atransaction at a transaction terminal.

In an embodiment, at 311, the transaction video clip managerautomatically requests the video clip based on a type of security eventassociated with one of the security events.

At 320, the transaction video clip manager receives the video clip froma cache of transaction video clips.

In an embodiment, at 321, the transaction video clip manager receivesthe video clip as configured amount of transaction video for thetransaction, wherein the configured amount is defined by the operatorwithin the interface.

At 330, the transaction video clip manager obtains transaction data forthe transaction and any security events raised for the transaction,wherein the transaction data and the security events are indexed andlinked to the video clip.

At 340, the transaction video clip manager provides the video clip, thetransaction data, and the security events within an interface forplaying the video clip by an operator of a management terminal.

In an embodiment, at 341, the transaction video clip manager initiatesthe video clip within the interface for playing at a starting locationdefined by a timestamp associated with a transaction item included inthe transaction data when the operator selects the transaction itemwithin the interface.

In an embodiment, at 342, the transaction video clip manager initiatesthe video clip within the interface for playing at a starting locationdefined by a timestamp associated with one of the security events whenthe operator selects that security event within the interface.

In an embodiment, at 343, the transaction video clip manager activates atransaction terminal status light of the transaction terminal with apredefined color or playing an audible sound over one or more storesecurity speakers when a security alert option is selected by theoperator within the interface.

It should be appreciated that where software is described in aparticular form (such as a component or module) this is merely to aidunderstanding and is not intended to limit how software that implementsthose functions may be architected or structured. For example, modulesare illustrated as separate modules, but may be implemented ashomogenous code, as individual components, some, but not all of thesemodules may be combined, or the functions may be implemented in softwarestructured in any other convenient manner.

Furthermore, although the software modules are illustrated as executingon one piece of hardware, the software may be distributed over multipleprocessors or in any other convenient manner.

The above description is illustrative, and not restrictive. Many otherembodiments will be apparent to those of skill in the art upon reviewingthe above description. The scope of embodiments should therefore bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

In the foregoing description of the embodiments, various features aregrouped together in a single embodiment for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting that the claimed embodiments have more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus, the following claims are herebyincorporated into the Description of the Embodiments, with each claimstanding on its own as a separate exemplary embodiment.

The invention claimed is:
 1. A method, comprising: caching a videostreamed from a camera and captured by the camera for a transaction areaof a transaction terminal in a cache, wherein caching further includesreceiving the video from the camera that is situated above or overheadof the transaction area, and wherein caching further includes offloadingthe video from the cache to storage on a server after a configuredperiod of time after the transaction ends; obtaining transaction dataassociated with a transaction occurring at the transaction terminal;linking the transaction data to portions of the video residing in thecache; receiving a request for a video clip of the transaction; andproviding the video clip and the transaction data to a managementterminal based on the request by taking a configured amount of the videofrom the cache that starts at a first configured time before an eventand continues through a second configured time after the event.
 2. Themethod of claim 1, wherein obtaining further includes obtaining one ormore security events raised by a security system for the transaction. 3.The method of claim 2, wherein linking further includes linking the oneor more security events to the portions or to other portions of thevideo residing in the cache.
 4. A method, comprising: caching a videostreamed from a camera and captured by the camera for a transaction areaof a transaction terminal in a cache; obtaining transaction dataassociated with a transaction occurring at the transaction terminal;linking the transaction data to portions of the video residing in thecache, wherein linking further includes indexing each item identified inthe transaction data with the corresponding portion of the video basedon timestamps associated with the corresponding item and thecorresponding portion of the video; receiving a request for a video clipof the transaction; and providing the video clip and the transactiondata to a management terminal based on the request by taking aconfigured amount of the video from the cache that starts at a firstconfigured time before an event and continues through a secondconfigured time after the event.
 5. The method of claim 4, whereinproviding further includes providing the transaction data as a list ofthe items, each item of the list having metadata, and wherein thecorresponding metadata associated with each item references a specifictime location within the video clip.
 6. The method of claim 1, whereinproviding further includes providing the transaction data and the videoclip to an interface of the management terminal.
 7. The method of claim6, wherein providing further includes processing an ApplicationProgramming Interface (API) to provide the transaction data and thevideo clip to the interface.
 8. The method of claim 1, wherein providingfurther includes providing the video clip to the management terminal asa link.
 9. A method, comprising: caching a video streamed from a cameraand captured by the camera for a transaction area of a transactionterminal in a cache; obtaining transaction data associated with atransaction occurring at the transaction terminal; linking thetransaction data to portions of the video residing in the cache;receiving a request for a video clip of the transaction; and providingthe video clip and the transaction data to a management terminal basedon the request by taking a configured amount of the video from the cachethat starts at a first configured time before an event and continuesthrough a second configured time after the event, wherein providingfurther includes receiving the first configured time and the secondconfigured time as a configuration setting from an operator of themanagement terminal.
 10. A method, comprising: caching a video streamedfrom a camera and captured by the camera for a transaction area of atransaction terminal in a cache; obtaining transaction data associatedwith a transaction occurring at the transaction terminal; linking thetransaction data to portions of the video residing in the cache;receiving a request for a video clip of the transaction; and providingthe video clip and the transaction data to a management terminal basedon the request by taking a configured amount of the video from the cachethat starts at a first configured time before an event and continuesthrough a second configured time after the event, wherein providingfurther includes identifying the event as a security event having atimestamp that corresponds to a specific location within the videostored in the cache.
 11. A method, comprising: requesting a video clipof a transaction at a transaction terminal, wherein requesting furtherincludes automatically requesting the video clip based on a type ofsecurity event associated with one of the security events; receiving thevideo clip from a cache of transaction video clips; obtainingtransaction data for the transaction and any security events raised forthe transaction, wherein the transaction data and the security eventsare indexed and linked to the video clip; and providing the video clip,the transaction data, and the security events within an interface forplaying the video clip by an operator of a management terminal.
 12. Amethod, comprising: requesting a video clip of a transaction at atransaction terminal, wherein receiving further includes receiving thevideo clip as configured amount of transaction video for thetransaction, wherein the configured amount is defined by an operatorwithin the interface; receiving the video clip from a cache oftransaction video clips; obtaining transaction data for the transactionand any security events raised for the transaction, wherein thetransaction data and the security events are indexed and linked to thevideo clip; and providing the video clip, the transaction data, and thesecurity events within an interface for playing the video clip by theoperator of a management terminal.
 13. The method of claim 11, whereinproviding further includes initiating the video clip within theinterface for playing at a starting location defined by a timestampassociated with a transaction item included in the transaction data whenthe operator selects the transaction item within the interface.
 14. Themethod of claim 11, wherein providing further includes initiating thevideo clip within the interface for playing at a starting locationdefined by a timestamp associated with one of the security events whenthe operator selects that security event within the interface.
 15. Themethod of claim 11 further comprising, activating a transaction terminalstatus light of the transaction terminal with a predefined color orplaying an audible sound over one or more store security speakers when asecurity alert option is selected by the operator within the interface.16. A system, comprising: a camera; a transaction terminal; a managementterminal comprising a terminal processor and a terminal non-transitorycomputer-readable storage medium having terminal executable instructionsrepresenting a terminal event interface; a server comprising a serverprocessor and a server non-transitory computer-readable storage mediumhaving server executable instructions representing a server eventinterface; the terminal event interface when executed by the terminalprocessor from the terminal non-transitory computer-readable storagemedium causes the terminal processor to perform processing comprising:providing the server event interface with an operator-defined period oftime; requesting a video clip from the server event interface for avideo of a transaction area at the transaction terminal during atransaction being processed at the transaction terminal; receiving thevideo clip from the server event interface; receiving transaction dataand any security events from the server event interface; presenting thevideo clip, the transaction data, and the security events on a displayof the management terminal; and playing the video clip on the displaybased on selections made by the operator of the transaction data and thesecurity events; the server event interface when executed by the serverprocessor from the server non-transitory computer-readable storagemedium causes the server processor to perform processing comprising:caching video provided by the camera in a cache; receiving a requestfrom the terminal event interface for the video clip; deriving the videoclip from the video in the cache by starting at a timestamped locationwithin the video that precedes a security event timestamp or atransaction start timestamp by the operator-defined period of time andcontinues passed the security event timestamp or the transaction starttimestamp by the operator-defined period of time; indexing and linkingthe transaction data and the security events to portions of the videoclip; and providing the video clip, the transaction data, and thesecurity events to the terminal event interface.
 17. The system of claim16, wherein the management terminal is a Self-Service Terminal (SST)configured as the management terminal, a Point-Of-Sale (POS) terminalconfigured as the management terminal, a teller terminal, a desktopcomputer, a laptop computer, a tablet computer, or a mobile phone.